From 298950dbe88deb0697fdd4f273f1583dc51d20cc Mon Sep 17 00:00:00 2001 From: Keir Fraser Date: Fri, 14 Dec 2007 10:12:15 +0000 Subject: [PATCH] docs/misc/xenstore.txt minor fixes Signed-off-by: Ian Jackson --- docs/misc/xenstore.txt | 20 +++++++++++++------- 1 file changed, 13 insertions(+), 7 deletions(-) diff --git a/docs/misc/xenstore.txt b/docs/misc/xenstore.txt index 3916403317..e0ad8f9b52 100644 --- a/docs/misc/xenstore.txt +++ b/docs/misc/xenstore.txt @@ -174,6 +174,17 @@ WATCH ||? away, with equal to . Watches may be triggered spuriously. The tx_id in a WATCH request is ignored. + Watches are supposed to be restricted by the permissions + system but in practice the implementation is imperfect. + Applications should not rely on being sent a notification for + paths that they cannot read; however, an application may rely + on being sent a watch when a path which it _is_ able to read + is deleted even if that leaves only a nonexistent unreadable + parent. A notification may omitted if a node's permissions + are changed so as to make it unreadable, in which case future + notifications may be suppressed (and if the node is later made + readable, some notifications may have been lost). + WATCH_EVENT || Unsolicited `reply' generated for matching modfication events as described above. req_id and tx_id are both 0. @@ -182,7 +193,7 @@ WATCH_EVENT || modifed; however if the event was the recursive removal of an parent of , is just (rather than the actual path which was removed). So - is a child of , regardless. + is a child of , regardless. Iff for the watch was specified as a relative pathname, the path will also be relative (with the same base, @@ -192,7 +203,7 @@ UNWATCH ||? ---------- Transactions ---------- -TRANSACTION_START ?? | +TRANSACTION_START | | is an opaque uint32_t allocated by xenstored represented as unsigned decimal. After this, transaction may be referenced by using (as 32-bit binary) in the @@ -202,11 +213,6 @@ TRANSACTION_START ?? | Currently xenstored has the bug that after 2^32 transactions it will allocate the transid 0 for an actual transaction. - Clients using the provided xs.c bindings will send a single - nul byte for the argument payload. We recommend that future - clients continue to do the same; any future extension will not - use that syntax. - TRANSACTION_END T| TRANSACTION_END F| tx_id must refer to existing transaction. After this -- 2.30.2